docs: mission control updates #8708
Merged
+1,519
−580
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
4 issues found across 59 files
Prompt for AI agents (all 4 issues)
Understand the root cause of the following 4 issues and fix them.
<file name="docs/docs.json">
<violation number="1" location="docs/docs.json:450">
`/mission-control/source-control` does not exist, so this new redirect will send `/hub/source-control` visitors to a 404. Please point the redirect at an existing Mission Control page instead.</violation>
</file>
<file name="docs/mission-control/sharing.mdx">
<violation number="1" location="docs/mission-control/sharing.mdx:31">
Fix the grammar so the sentence refers to multiple items (e.g., "Public or Private items") to keep the documentation clear.</violation>
</file>
<file name="docs/customization/models.mdx">
<violation number="1" location="docs/customization/models.mdx:107">
The gpt-oss-20b setup instructions now point to `ttps://hub.continue.dev/...`, so the hyperlink is broken. Please correct it to `https://` so the documentation link works.</violation>
</file>
<file name="docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx">
<violation number="1" location="docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx:49">
Update the Mission Control secrets link to use the new /mission-control/secrets/secret-types path so readers don’t hit the removed /hub page.</violation>
</file>
React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.
|
|
||
| <Step title="Add your API key"> | ||
| Add your API key to Continue. See [adding secrets in Continue Hub](/hub/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables) | ||
| Add your API key to Continue. See [adding secrets in Continue Mission Control](/hub/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables) |
Contributor
There was a problem hiding this comment.
Update the Mission Control secrets link to use the new /mission-control/secrets/secret-types path so readers don’t hit the removed /hub page.
Prompt for AI agents
Address the following comment on docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx at line 49:
<comment>Update the Mission Control secrets link to use the new /mission-control/secrets/secret-types path so readers don’t hit the removed /hub page.</comment>
<file context>
@@ -32,28 +32,28 @@ Go to the [API keys page](https://router.tetrate.ai/api-keys) to get your key
<Step title="Add your API key">
-Add your API key to Continue. See [adding secrets in Continue Hub](/hub/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables)
+Add your API key to Continue. See [adding secrets in Continue Mission Control](/hub/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables)
<Tip>
-Add it as a Continue Hub secret named `TETRATE_API_KEY` to reuse across projects.
</file context>
Suggested change
| Add your API key to Continue. See [adding secrets in Continue Mission Control](/hub/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables) | |
| Add your API key to Continue. See [adding secrets in Continue Mission Control](/mission-control/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables) |
Contributor
There was a problem hiding this comment.
2 issues found across 17 files (reviewed changes from recent commits).
Prompt for AI agents (all 2 issues)
Understand the root cause of the following 2 issues and fix them.
<file name="docs/guides/snyk-mcp-continue-cookbook.mdx">
<violation number="1" location="docs/guides/snyk-mcp-continue-cookbook.mdx:114">
Please keep the sentence grammatical by retaining the article: "The Mission Control listing automatically configures the MCP command."</violation>
</file>
<file name="docs/mission-control/configs/intro.mdx">
<violation number="1" location="docs/mission-control/configs/intro.mdx:99">
Please update the sentence to read "the Mission Control interface" and replace the remaining "hub-managed" phrasing so the branding stays consistent.</violation>
</file>
React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.
Contributor
There was a problem hiding this comment.
1 issue found across 7 files (reviewed changes from recent commits).
Prompt for AI agents (all 1 issues)
Understand the root cause of the following 1 issues and fix them.
<file name="docs/mission-control/integrations/slack-agent.mdx">
<violation number="1" location="docs/mission-control/integrations/slack-agent.mdx:32">
The colon is immediately followed by the link text, so this renders as `from:Integrations Settings` and reads awkwardly. Please add a space after the colon so the sentence is legible.</violation>
</file>
React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.
|
|
||
| - [Personal Integrations Settings](https://hub.continue.dev/settings/integrations) | ||
| - Org Integrations Settings - `https://hub.continue.dev/organizations/{your-org}/settings/integrations` | ||
| Continue's Slack Bot can be installed to a Slack workspace via Mission Control, from:[Integrations Settings](https://hub.continue.dev/integrations) |
Contributor
There was a problem hiding this comment.
The colon is immediately followed by the link text, so this renders as from:Integrations Settings and reads awkwardly. Please add a space after the colon so the sentence is legible.
Prompt for AI agents
Address the following comment on docs/mission-control/integrations/slack-agent.mdx at line 32:
<comment>The colon is immediately followed by the link text, so this renders as `from:Integrations Settings` and reads awkwardly. Please add a space after the colon so the sentence is legible.</comment>
<file context>
@@ -29,10 +29,7 @@ Mention @Continue in any channel with a task description, and it will:
-
-- [Personal Integrations Settings](https://hub.continue.dev/settings/integrations)
-- Org Integrations Settings - `https://hub.continue.dev/organizations/{your-org}/settings/integrations`
+Continue's Slack Bot can be installed to a Slack workspace via Mission Control, from:[Integrations Settings](https://hub.continue.dev/integrations)
<Warning>
</file context>
Suggested change
| Continue's Slack Bot can be installed to a Slack workspace via Mission Control, from:[Integrations Settings](https://hub.continue.dev/integrations) | |
| Continue's Slack Bot can be installed to a Slack workspace via Mission Control, from [Integrations Settings](https://hub.continue.dev/integrations) |
bdougie
previously approved these changes
Nov 13, 2025
Collaborator
bdougie
left a comment
bdougie
left a comment
There was a problem hiding this comment.
I went through each file and name changes look good. Also I think the files do a great job of introducing concepts for the Mission Control feature. I want to avoid going into specific details since we will be updating this based on user feedback a lot in the coming weeks.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request updates documentation throughout the project to rename "Continue Hub" to "Continue Mission Control" for consistency and clarity. The changes affect references in guides, configuration instructions, and UI descriptions, as well as internal and external links.
Most important changes:
Global terminology and documentation updates:
File and section renaming:
Link and UI reference updates:
These updates ensure that all documentation is aligned with the new "Continue Mission Control" branding and provide a clearer experience for users navigating the platform.
closes CON-4841
AI Code Review
@continue-reviewChecklist
Screen recording or screenshot
[ When applicable, please include a short screen recording or screenshot - this makes it much easier for us as contributors to review and understand your changes. See this PR as a good example. ]
Tests
[ What tests were added or updated to ensure the changes work as expected? ]
Summary by cubic
Renamed “Continue Hub” to “Continue Mission Control” across the docs and expanded Mission Control with Tasks, Workflows, Sharing, Metrics, and integrations (GitHub, Sentry, Slack). Implements the branding and navigation updates requested in CON-4841.
New Features
Refactors
Written for commit e37ac0b. Summary will update automatically on new commits.